Repository navigation
ci: 🚀 deploy the website after each release, from GitHub Actions - #74
Merged
Merged
Conversation
Vercel built the website on every push, a library change or a release commit too, and before the new version was on npm. The website now deploys from GitHub Actions (website.yml, with the Vercel CLI: the build runs with the CI's pnpm and Node, and Vercel serves it), only: - after each release, once the version is public on npm: release.yml waits for the approval (`npm stage approve`, up to 6 hours), publishes the GitHub release that was a draft, and calls it; - on a push to main that changes website/ or vercel.json; - by hand. Vercel builds nothing from Git for main any more. A branch that changes website/ or vercel.json, compared with main, still gets a preview from its Git integration (website/scripts/vercel-preview.sh, its Ignored Build Step); the rest are skipped. The deploy needs VERCEL_TOKEN, VERCEL_ORG_ID and VERCEL_PROJECT_ID as secrets, `.vercel` is ignored, and CONTRIBUTING and the website's README describe the flow.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vercel built the website on every push, a library change or a release
commit too, and before the new version was on npm. The website now
deploys from GitHub Actions (website.yml, with the Vercel CLI: the build
runs with the CI's pnpm and Node, and Vercel serves it), only:
waits for the approval (
npm stage approve, up to 6 hours), publishesthe GitHub release that was a draft, and calls it;
Vercel builds nothing from Git for main any more. A branch that changes
website/ or vercel.json, compared with main, still gets a preview from
its Git integration (website/scripts/vercel-preview.sh, its Ignored
Build Step); the rest are skipped. The deploy needs VERCEL_TOKEN,
VERCEL_ORG_ID and VERCEL_PROJECT_ID as secrets,
.vercelis ignored,and CONTRIBUTING and the website's README describe the flow.
Stack created with GitHub Stacks CLI • Give Feedback 💬